Skip to content

Fixes to make it compile and work from Sdk 21 to 36 - #978

Open
AlainKnaff wants to merge 52 commits into
klausw:masterfrom
AlainKnaff:master
Open

Fixes to make it compile and work from Sdk 21 to 36#978
AlainKnaff wants to merge 52 commits into
klausw:masterfrom
AlainKnaff:master

Conversation

@AlainKnaff

Copy link
Copy Markdown

Copied gradle-wrapper.jar from another project, and then used gradlew to compile it, slowly increasing gradle version and Sdk, and addressing errors and warnings at each step.

There are still (non-fatal) Lint warnings left.

Alain Knaff added 29 commits January 17, 2026 09:52
…espace, and only have the "misfortune" of using "sacred" android shortcut prefix for it
@AlainKnaff

Copy link
Copy Markdown
Author

Correction: minSdkVersion needs to be reduced to 34 or else bottom of keyboard hides behind navbar on Android 16.

Probably there's a way to fix this using android:fitsSystemWindows="true", but unfortunately I don't know how to specify this for the keyboard itself.

@AlainKnaff

Copy link
Copy Markdown
Author

Probably there's a way to fix this using android:fitsSystemWindows="true", but unfortunately I don't know how to specify this for the keyboard itself.

Found it. In the end, keyboard layouts (the input_*.xml files) work just like any other layout, and do understand android:fitsSystemWindows="true" after all. So it's Sdk 36 again.

Commit 81457ca, the pull request doesn't seem to pick it up automatically any longer...

Alain Knaff and others added 19 commits January 20, 2026 11:50
…de. Apparently, the Keyboard class uses display dimensions for its internal width calculations, rather than view dimensions, so whatever width is specified in layout/input_*.xml is being ignored.
This fixes an issue where clicking into second-level settings screens would cause the app to crash with an `android.content.ActivityNotFoundException`.
Fix crash when entering second-level settings screens

This was indeed needed to navigate to subpages of settings, just checked.
It's weird though, as normally exported should only apply to intents sent from *outside* the application, not for navigation within. Something to investigate for later.
@jimklimov

Copy link
Copy Markdown

Great, and thanks for releasing APKs.

I had to uninstall the original HK and so re-enter my custom setup, but it works :)

@jimklimov

jimklimov commented Apr 23, 2026

Copy link
Copy Markdown

@AlainKnaff : thanks again. Some notes after a couple of weeks usage on Xiaomi Redmi Note 14, Android 15:

  • I saw the navbar over keyboard once or twice, but "back"ing out to close the keyboard, and tapping into text input area opened it in a correct location/size.
  • Rather often (enough to notice, a few times per week) the keyboard pops out unexpected, like on the desktop over the icons.
    • When it does so over apps, this is quite disruptive actually: they do not know of it, window sizes do not adjust, bottom half is just obscured; worse, when I habitually press navbar Back to hide the keyboard, actually the app gets that event and does something I usually did not want it to.
    • Example (Firefox tab-list window has no input for text, but the keyboard just appeared; original HK build never did that):
Screenshot_2026-04-25-10-35-04-552_org mozilla firefox
  • The navbar is now gray not black like before, sometimes with kbd buttons visible. I think the navbar window tries to render a keyboard of its own?
    • IMG_20260423_093929
    • IMG_20260423_093852

dark-penguin and others added 3 commits May 18, 2026 20:03
This reverts commit c31b267.

That commit causes more problems than it fixes: popup items
are not triggered unless you move your finger up towards them.
@jimklimov

Copy link
Copy Markdown

UPDATE: I've been using https://github.com/AlainKnaff/hackerskeyboard/releases/tag/1.42.8ak for the past month or so, and most of the annoyance from the previous post still applies. The problems resolved since the last original release by @klausw do also apply, thanks to both :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants